home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Collection of Internet
/
Collection of Internet.iso
/
infosrvr
/
dev
/
www_talk.930
/
001159_sanders@bsdi.com _Wed May 19 19:19:58 1993.msg
< prev
next >
Wrap
Internet Message Format
|
1994-01-24
|
3KB
Return-Path: <sanders@bsdi.com>
Received: from dxmint.cern.ch by nxoc01.cern.ch (NeXT-1.0 (From Sendmail 5.52)/NeXT-2.0)
id AA02664; Wed, 19 May 93 19:19:58 MET DST
Errors-To: sanders@bsdi.com
Received: from austin.BSDI.COM by dxmint.cern.ch (5.65/DEC-Ultrix/4.3)
id AA11773; Wed, 19 May 1993 19:41:01 +0200
Received: from localhost by austin.BSDI.COM (5.67/1.37)
id AA04120; Wed, 19 May 93 12:40:51 -0500
Message-Id: <9305191740.AA04120@austin.BSDI.COM>
To: www-talk@nxoc01.cern.ch
Subject: MIME and HTRQ/V1.0 question
Errors-To: sanders@bsdi.com
Reply-To: sanders@bsdi.com
Organization: Berkeley Software Design, Inc.
Date: Wed, 19 May 1993 12:40:51 -0500
From: Tony Sanders <sanders@bsdi.com>
When returning a document of unknown content what should the header
format say?
Options as I see it are:
1 Content-type: text/plain\n\n[raw data]
2 Context-type: text/html\n\n<PLAINTEXT>\n[raw data]
[Is <PLAINTEXT> being depreciated?]
3 Context-type: application/binary [for binary files and]
Context-type: text/plain [for text files]
I'm assuming option #3 unless I hear otherwise. It will work well
if browers do something like <PLAINTEXT> for text/plain and
pop up a save file dialog for application/binary.
Marc: How is Mosaic going to handle things like .cave files?
are there going to be MIME types added for stuff like this?
Here are my current plans.
# XXX: need to make tar, uu, z, and Z be encodings
#
$ext{'aiff'} = $ext{'AIFF'} = 'application/binary';
$ext{'au'} = $ext{'AU'} = 'application/binary';
$ext{'snd'} = $ext{'SND'} = 'application/binary';
$ext{'cave'} = $ext{'CAVE'} = 'application/binary';
$ext{'dvi'} = $ext{'DVI'} = 'application/dvi';
$ext{'evlm'} = $ext{'EVLM'} = 'application/binary';
$ext{'gif'} = $ext{'GIF'} = 'image/binary';
$ext{'html'} = $ext{'HTML'} = 'text/html';
$ext{'jpeg'} = $ext{'JPEG'} = 'image/jpeg';
$ext{'jpg'} = $ext{'JPG'} = 'image/jpeg';
$ext{'mime'} = $ext{'MIME'} = 'application/binary';
$ext{'movie'} = $ext{'MOVIE'} = 'application/binary';
$ext{'mpeg'} = $ext{'MPEG'} = 'application/binary';
$ext{'mpg'} = $ext{'MPG'} = 'application/binary';
$ext{'ps'} = $ext{'PS'} = 'application/postscript';
$ext{'rgb'} = $ext{'RGB'} = 'application/binary';
$ext{'rtf'} = $ext{'RTF'} = 'application/binary';
$ext{'tar'} = $ext{'TAR'} = 'application/binary';
$ext{'hqx'} = $ext{'HQX'} = 'application/binary';
$ext{'uu'} = $ext{'UU'} = 'application/binary';
$ext{'tex'} = $ext{'TEX'} = 'application/binary';
$ext{'tiff'} = $ext{'TIFF'} = 'application/binary';
$ext{'tif'} = $ext{'TIF'} = 'application/binary';
$ext{'txt'} = $ext{'TXT'} = 'application/binary';
$ext{'text'} = $ext{'TEXT'} = 'application/binary';
$ext{'xbm'} = $ext{'XBM'} = 'image/xbitmap';
$ext{'xwd'} = $ext{'XWD'} = 'image/xwindowdump';
$ext{'z'} = $ext{'Z'} = 'application/binary'; # different!
I also need to figure out how to the the encoding stuff work
for MIME. Guess I need to study the RFC for a while.
Comments/suggestions? lemme know
--sanders@bsdi.com